System, method, and computer program product for sending remote device configuration information to a monitor using e-mail

ABSTRACT

In a monitoring system for networked devices, a system, method, and computer program product for obtaining a globally-unique identifier for a network device, and sending the same to a central monitor responsible for monitoring devices on multiple networks. A remote monitoring workstation monitors devices connected to a network using IP-based SNMP commands and stores the device monitoring information in a database. The remote monitoring workstation queries the database to obtain an IP address and the collected monitoring information for a device, uses the IP address to request a globally-unique identifier (e.g., a MAC address) from a device using SNMP commands, then sends the monitoring information including the globally-unique device identifier to a central monitoring workstation via an e-mail message.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application is related to U.S. patent applicationSer. No. 09/190,460, filed Nov. 13, 1998, entitled “Method and Systemfor Translating Documents Using Different Translation Resources forDifferent Portions of the Documents,” which is a continuation of U.S.patent application Ser. No. 08/654,207, filed May 28, 1996, entitled“Method and System for Translating Documents Using Different TranslationResources for Different Portions of the Documents,” now U.S. Pat. No.5,848,386; U.S. patent application Ser. No. 08/997,705, filed Dec. 23,1997, entitled “Object-oriented System and Computer Program Product forMapping Structured Information to Different Structured Information,” nowU.S. Pat. No. 6,085,196; U.S. patent application Ser. No. 08/997,705,filed Dec. 23, 1997, entitled “Method and Apparatus for Providing aGraphical User Interface for Creating and Editing a Mapping of a FirstStructural Description to a Second Structural Description”; U.S. patentapplication Ser. No. 09/756,120, filed Jan. 9, 2001, entitled “Methodand System of Remote Support Of Device Using Email”; U.S. patentapplication Ser. No. 09/668,162, filed Sep. 25, 2000, entitled “Methodand System of Data collection and Mapping From a Remote PositionReporting Device”; U.S. patent application Ser. No. 09/575,710, filedJul. 25, 2000, entitled “Method and System of Remote Diagnostic andInformation Collection and Service System”; U.S. patent application Ser.No. 09/575,702, filed Jul. 12, 2000, entitled “Method and System ofRemote Position Report Device”; U.S. patent application Ser. No.09/453,934, filed May 17, 2000, entitled “Method and System of RemoteDiagnostic, Control and Information Collection Using a Dynamic LinkedLibrary for Multiple Formats and Multiple Protocols”; U.S. patentapplication Ser. No. 09/453,935, filed May 17, 2000, entitled “Methodand System of Remote Diagnostic, Control and Information CollectionUsing a Dynamic Linked Library of Multiple Formats and MultipleProtocols With Intelligent Protocol Processor”; U.S. patent applicationSer. No. 09/453,937, filed May 17, 2000, entitled “Method and System ofRemote Diagnostic, Control and Information Collection Using a DynamicLinked Library of Multiple Formats and Multiple Protocols WithRestriction on Protocol”; U.S. patent application Ser. No. 09/453,936,filed May 17, 2000, entitled “Method and System of Remote Diagnostic,Control and Information Collection Using a Dynamic Linked Library ofMultiple Formats and Multiple Protocols with Intelligent Formatter”;U.S. patent application Ser. No. 09/542,284, filed Apr. 4, 2000,entitled “System and Method to Display Various Messages While Performingthe Tasks or While Idling”; U.S. patent application Ser. No. 09/520,368,filed on Mar. 7, 2000, entitled “Method and System for Updating theDevice Driver of a Business Office Appliance”; U.S. patent applicationSer. No. 09/453,877, filed Feb. 4, 2000, entitled “Method and System forMaintaining a Business Office Appliance through Log Files”; U.S. patentapplication Ser. No. 09/440,692, filed Nov. 16, 1999, entitled “Methodand System to Monitor the Application Usage and Send Back theInformation Using Connection and Connectionless Mode”; U.S. patentapplication Ser. No. 09/440,693, filed Nov. 16, 1999, entitled “Methodand System of Remote Diagnostic, Control and Information CollectionUsing a Dynamic Linked Library”; U.S. patent application Ser. No.09/440,647, filed Nov. 16, 1999, entitled “Method and System to Monitorthe Application Usage and Send Back the Information Using Connection andConnectionless Mode”; U.S. patent application Ser. No. 09/440,646, filedNov. 16, 1999, entitled “Method and System to Monitor the ApplicationUsage and Send Back the Information Using Connection and ConnectionlessMode”; U.S. patent application Ser. No. 09/440,645, filed Nov. 16, 1999,entitled “Application Unit Monitoring and Reporting System and MethodWith Usage Data Logged Into a Map Structure”; U.S. patent applicationSer. No. 09/408,443, filed Sep. 29, 1999, entitled “Method and Systemfor Remote Diagnostic, Control, and Information Collection Based onvarious Communication Modes for Sending Messages to a Resource Manager”;U.S. patent application Ser. No. 09/407,769, filed Sep. 29, 1999,entitled “Method and System for Remote Diagnostic, Control andInformation Collection Based on various Communication Modes for SendingMessages to Users”; U.S. patent application Ser. No. 09/393,677, filedSep. 10, 1999, entitled “Application Unit Monitoring and ReportingSystem and Method”; U.S. patent application Ser. No. 09/311,148, filedMay 13, 1999, entitled “Application Unit Monitoring and Reporting Systemand Method”; U.S. patent application Ser. No. 09/192,583, filed Nov. 17,1998, entitled “Method and System for Communicating With a DeviceAttached to a Computer Using Electronic Mail Messages”; U.S. patentapplication Ser. No. 08/883,492, filed Jun. 26, 1997, entitled “Methodand System for Diagnosis and Control of Machines Using ConnectionlessModes Having Delivery Monitoring and an Alternate Communication Mode”;U.S. patent application Ser. No. 08/820,633, filed Mar. 19, 1997,entitled “Method and System to Diagnose a Business Office Device Basedon Operating Parameters Set by a User,” now U.S. Pat. No. 5,887,216;U.S. patent application Ser. No. 08/733,134, filed Oct. 16, 1996,entitled “Method and System for Diagnosis and Control of Machines UsingConnectionless Modes of Communication,” now U.S. Pat. No. 5,909,493;U.S. patent application Ser. No. 08/880,683, filed Jun. 23, 1997, U.S.patent applications Ser. Nos. 09/107,989 and 09/108,705, both of whichwere filed Jul. 1, 1998, all three of which are entitled “Method andSystem for Controlling and Communicating, with Machines Using MultipleCommunication Formats,” and all three of which are divisions of U.S.patent application Ser. No. 08/624,228, filed Mar. 29, 1996, entitled“Method and System for Controlling and Communicating with Machines UsingMultiple Communication Formats,” now U.S. Pat. No. 5,818,603; U.S.patent application Ser. No. 09/457,669, entitled “Method and System forDiagnosis and Control of Machines Using Connection and ConnectionlessModes of Communication,” filed Dec. 9, 1999, which is a continuation ofU.S. patent application Ser. No. 08/916,009, entitled “Method and Systemfor Diagnosis and Control of Machines Using Connection andConnectionless Modes of Communication,” filed Aug. 21, 1997, which is acontinuation of U.S. patent application Ser. Nos. 08/738,659 and08/738,461, filed Oct. 30, 1996, both of which are entitled “Method andSystem for Diagnosis and Control of Machines Using Connection andConnectionless Modes of Communication,” which are divisions of U.S.patent application Ser. No. 08/463,002, filed Jun. 5, 1995, entitled“Method and System for Diagnosis and Control of Machines UsingConnection and Connectionless Modes of Communication”, now U.S. Pat. No.5,819,110; U.S. patent application Ser. No. 08/852,413, filed May 7,1987, entitled “Method and System for Controlling and Communicating withBusiness Office Devices,” now U.S. Pat. No. 5,774,678, which is acontinuation of U.S. patent application Ser. No. 08/698,068, filed Aug.15, 1996, entitled “Method and Apparatus for Controlling andCommunicating With Business Office Devices”, now U.S. Pat. No.5,649,120, which is a continuation of U.S. patent application Ser. No.08/562,192, filed Nov. 22, 1995, now U.S. Pat. No. 5,568,618, entitled“Method and Apparatus for Controlling and Communicating With BusinessOffice Devices”, which is a continuation of U.S. patent application Ser.No. 08/473,780, filed Jun. 6, 1995, entitled “Method and Apparatus forControlling and Communicating With Business Office Devices”, now U.S.Pat. No. 5,544,289, which is a continuation of U.S. patent applicationSer. No. 08/426,679, filed Apr. 24, 1995, entitled “Method and Apparatusfor Controlling and Communicating With Business Office Devices,” nowU.S. Pat. No. 5,537,554, which is a continuation of U.S. patentapplication Ser. No. 08/282,168, filed Jul. 28, 1994, entitled “Methodand Apparatus for Controlling and Communicating With Business OfficeDevices”, now U.S. Pat. No. 5,412,779, which is a continuation of U.S.patent application Ser. No. 07/902,462, filed Jun. 19, 1992, nowabandoned, which is a continuation of U.S. patent application Ser. No.07/549,278, filed Jul. 6, 1990, now abandoned; U.S. patent applicationSer. No. ______, filed ______, 2001, entitled “SYSTEM, METHOD, ANDCOMPUTER PROGRAM PRODUCT FOR SENDING PERSISTENT AND NON-PERSISTENTSTATUS INFORMATION TO A MONITOR USING E-MAIL” (Attorney Docket Number205828US-5244-5244-2); and U.S. Patent Application ______, filed ______,2001, entitled “SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FORTRANSFERRING REMOTE DEVICE SUPPORT DATA TO A MONITOR USING E-MAIL”(Attorney Docket Number 205840US-5244-5244-2), the entire contents ofeach of these applications and patents are incorporated herein byreference.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] This invention relates to systems, methods, and computer programproducts for monitoring networked devices. More particularly, tosystems, methods, and computer program products for centrally monitoringdevices connected to multiple networks while allowing for networkaddress reuse among networks and network address-based monitoring withina network.

[0004] 2. Discussion of the Background

[0005] Co-pending U.S. patent application Ser. No. 09/756,120 filed onJan. 9, 2001, describes a system for remotely monitoring networkeddevices using e-mail. As described in that application, the SimpleNetwork Management Protocol (SNMP) is used by a remote monitor tocollect information from networked devices. The collected information isthen sent to a central monitor using, for example, e-mail.

[0006] Devices connected to a network may be monitored by sending SNMPcommands to the various devices based on their IP addresses. The deviceswill then respond to the SNMP queries with the requested information.The IP addresses of the devices are used to uniquely identify eachdevice on a network. However, an IP address is not necessarily aglobally-unique identifier for a particular device. For example, it isknown to use network address translators (NAT) as an approach to reusingIP addresses on different networks. A NAT allows a network to have oneor more globally-unique addresses by which they are known to the outsideworld (e.g., the Internet), without requiring that each node of thenetwork behind the NAT have a globally unique IP address. This approachallows, for example, a company to reuse IP addresses on their differentinternal networks while still providing one or more globally-uniqueidentifier(s) to the outside world.

[0007] These addressing complexities present difficulties toapplications that wish to maintain information on the individual devicesof a plurality of networks that may or may not share IP addresses. Itwould be desirable to have the ability to monitor network devicesconnected to multiple networks from a common central monitoringlocation. However, device address ambiguities increases the complexityof providing such a capability.

SUMMARY OF THE INVENTION

[0008] The inventors of the present invention have recognized that itwould be advantageous for devices connected to multiple networks to haveglobally-unique identifiers that would enable them to be monitored froma central monitor that may or may not be connected to one of thenetworks having devices to be monitored. The inventors of the presentinvention have recognized that it would be further advantageous if IPaddress reuse and the ability to monitor devices within a network viaSNMP were not sacrificed in providing a solution to device addressambiguity.

[0009] The present invention provides a system, method, and computerprogram product through which devices residing on multiple networks maybe locally monitored using, for example, IP-based SNMP, and centrallymonitored without device address ambiguity, and which allows IP addressreuse across networks including devices to be monitored by a centrallocation. In one embodiment of the present invention, a remotemonitoring workstation monitors devices connected to a network usingIP-based SNMP commands and stores the device monitoring information in adatabase. The remote monitoring workstation queries the database toobtain an IP address and the collected monitoring information for adevice, uses the IP address to request a globally-unique identifier(e.g., a MAC address) from a device using SNMP commands, then sends themonitoring information including the globally-unique device identifierto a central monitoring workstation via an e-mail message.

[0010] One advantage of the present invention is that devices frommultiple networks may be monitored from a central location without theneed for additional processing to resolve device address ambiguities.Another advantage of the present invention is the devices connected toany particular network may continue to be monitored using an IP-basedprotocol, such as SNMP. Moreover, since address ambiguities are resolvedby, for example, a MAC address, prior to sending the monitoringinformation to a central monitor, there is no requirement that thedevices being monitored have globally-unique IP addresses, therebyallowing the present invention to be used in networks that include, forexample, NATs.

[0011] Consistent with the title of this section, the above summary isnot intended to be an exhaustive discussion of all the features orembodiments of the present invention. A more complete, although notnecessarily exhaustive, description of the features and embodiments ofthe invention is found in the section entitled “DESCRIPTION OF THEPREFERRED EMBODIMENTS.”

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] A more complete appreciation of the invention and many of theattendant advantages thereof will be readily obtained as the samebecomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings, wherein:

[0013]FIG. 1 illustrates three networked business office devicesconnected to a network of computers and databases through the Internet;

[0014]FIG. 2 illustrates the components of a digital image formingapparatus;

[0015]FIG. 3 illustrates the electronic components of the digital imageforming apparatus illustrated in FIG. 2;

[0016]FIG. 4 illustrates details of a multi-port communication interfaceillustrated in FIG. 3;

[0017]FIG. 5 illustrates an alternative system configuration in whichbusiness office devices are either connected directly to the network orconnected to a computer which is connected to the network;

[0018]FIG. 6A is a block diagram illustrating a flow of information toand from an application unit using electronic mail;

[0019]FIG. 6B illustrates an alternative way of communicating usingelectronic mail in which a computer that is connected to the applicationunit also serves as a Message Transfer Agent (MTA);

[0020]FIG. 6C illustrates an alternative way of communicating usingelectronic mail in which an application unit includes a message transferagent for exchanging electronic mail;

[0021]FIG. 6D illustrates an alternative way of communicating usingelectronic mail in which a mail server acts as a POP3 server to receivemail for an appliance/device and as an Simple Mail Transfer Protocol(SMTP) server to send mail for the appliance/device;

[0022]FIG. 7 illustrates an alternative manner of sending messagesacross the Internet;

[0023]FIG. 8 illustrates an exemplary computer which may be connected toan appliance/device and used to communicate electronic mail messages;

[0024]FIG. 9 illustrates an overall system configuration related to thepresent invention;

[0025]FIG. 10A illustrates a general software architecture of a messagesending module;

[0026]FIG. 10B illustrates a general software architecture of a messagereceiving module;

[0027]FIG. 11 illustrates a general architecture of a message sendingmodule;

[0028]FIG. 12 illustrates a general architecture of a message receivingmodule;

[0029]FIG. 13A is a flowchart illustrating a process implemented by thedevice information module shown in FIG. 11;

[0030]FIG. 13B illustrates a class structure of the device informationmodule;

[0031]FIG. 14 is a collaboration diagram for the device informationmodule;

[0032]FIG. 15A is a flowchart illustrating a process implemented by thedevice monitor module shown in FIG. 11;

[0033]FIG. 15B illustrates a class structure of the device monitormodule;

[0034]FIGS. 16, 17 and 18 are collaboration diagrams for the devicemonitor module;

[0035]FIG. 19A is a flowchart illustrating a process implemented by thedata transfer module shown in FIG. 11;

[0036]FIG. 19B is a flowchart illustrating a process for sendinginformation according to one embodiment of the present invention;

[0037]FIG. 19C illustrates a class structure of the data transfermodule;

[0038]FIGS. 20A, 21, 22, and 23 are collaboration diagrams for the datatransfer module in transferring information to monitoring site;

[0039]FIG. 20B illustrates an exemplary MIME attachment includingconfiguration information according to one embodiment of the presentinvention;

[0040]FIG. 20C illustrates an exemplary MIME attachment including statusinformation according to one embodiment of the present invention; and

[0041]FIG. 24 illustrates a class diagram of the Open DatabaseConnectivity (ODBC) interface module.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0042] Referring now to the drawings, and more particularly to FIG. 1thereof, there are illustrated (1) various machines and (2) computersfor monitoring, diagnosing and controlling the operation of themachines. In FIG. 1, there is a first network 16, such as a Local AreaNetwork (LAN) connected to computer workstations 17, 18, 20 and 22. Theworkstations can be any type of computers including, e.g., IBM PersonalComputer compatible devices, Unix-based computers, Linux-based computersor Apple Macintoshes. Also connected to the network 16 are (1) a digitalimage forming apparatus 24, (2) a facsimile machine 28, and (3) aprinter 32. As would be appreciated by one of ordinary skill in the art,two or more of the components of the digital image forming apparatus 24and the facsimile machine 28 can be combined into a unified “imageforming apparatus.” The devices 24, 28 and 32 and the workstations 17,18, 20 and 22 are referred to as machines or monitored devices and othertypes of devices may be used as the machines or monitored devices,including any of the devices discussed below. In some configurations,one or more workstations may be converted to business office appliances.One example of such a business office appliance is eCabinet from Ricoh,which was demonstrated at Fall Comdex in 1999 at Las Vegas. Also, afacsimile server (not illustrated) may be connected to the network 16and have a telephone, Integrated Services Digital Network (ISDN), cableor wireless connection. In addition to the digital image formingapparatus 24, facsimile machine 28, and printer 32 being connected tothe network 16, these devices may also include conventional telephoneand/or ISDN and/or cable and/or wireless connections 26, 30 and 34,respectively. As is explained below, the business office machines,business devices, or business office appliances 24, 28 and 32communicate with a remote monitoring, diagnosis, and control station,also referred to as a monitoring device, through, for example, theInternet via the network 16 or by a direct telephone, ISDN, wireless, orcable connection.

[0043] In FIG. 1, a wide area network (WAN) (e.g., the Internet or itssuccessor) is generally designated by 10. The WAN 10 can be either aprivate WAN, a public WAN or a hybrid. The WAN 10 includes a pluralityof interconnected computers and routers designated by 12A-12I. Themanner of communicating over a WAN is known through a series of Requestfor Comments (RFC) documents available from the Internet EngineeringTask Force (IETF) at http://www.ietf.org/rfc.html, including RFC 821entitled “Simple Mail Transfer Protocol”; RFC 822 entitled “Standard forthe Format of ARPA Internet Text Message”; RFC 959 entitled “FileTransfer Protocol (FTP)”; RFC 2045 entitled “Multipurpose Internet MailExtensions (MIME) Part One: Format of Internet Message Bodies”; RFC 1894entitled “An Extensible Message Format for Delivery StatusNotifications”; RFC 1939 entitled “Post Office protocol—Version 3”; andRFC 2298 entitled “An Extensible Message Format for Message DispositionNotifications.” The contents of each of these references areincorporated herein by reference.

[0044] Transmission Control Protocol/Internet Protocol (TCP/IP) relatedcommunication is described, for example, in the book “TCP/IPIllustrated,” Vol. 1, The Protocols, by W. R. Stevens, fromAddison-Wesley Publishing Company, 1994, the entire contents of which isincorporated herein by reference. Volumes 1-3 of “Internetworking withTCP/IP” by Comer and Stevens are also incorporated herein by referencein their entirety.

[0045] In FIG. 1, a firewall 50A is connected between the WAN 10 and thenetwork 16. A firewall is a device that allows only authorized computerson one side of the firewall to access a network, computers or individualparts on the other side of the firewall. Firewalls are known andcommercially available devices and/or software (e.g., SunScreen from SunMicrosystems Inc.). Similarly, firewalls 50B and 50C separate the WAN 10from a network 52 and a workstation 42, respectively. Additional detailson firewalls can be found in “Firewalls and Internet Security” by W. R.Cheswick, and S. M. Bellovin, 1994, AddisonWesley Publishing, and“Building Internet Firewalls” by D. B. Chapman and E. D. Zwicky, 1995,O'Reilly & Associates, Inc. The entire contents of those two referencesare incorporated herein by reference.

[0046] The network 52 is a conventional network and includes a pluralityof workstations 56, 62, 68 and 74. These workstations may be indifferent departments (e.g., marketing, manufacturing, designengineering, and customer service departments) within a single company.In addition to the workstations connected via the network 52, there is aworkstation 42, which is not directly connected to the network 52.Information in a database stored in a disk 46 may be shared using properencryption and protocols over the WAN 10 to the workstations connecteddirectly to the network 52. Also, the workstation 42 includes a directconnection to a telephone line and/or an ISDN and/or a cable and/or awireless network 44, and the database in disk 46 may be accessed throughthe telephone line, the ISDN, the cable or wirelessly. The cable used bythis invention may be implemented using a cable that is typically usedto carry television programming, a cable that provides for high-speedcommunication of digital data typically used with computers or the like,or any other desired type of cable.

[0047] Information of the business office machines, business devices orbusiness office appliances 24, 28 and 32 may be stored in one or more ofthe databases stored in the disks 46, 54, 58, 64, 70 and 76. Knowndatabases include (1) SQL databases by Microsoft, IBM, Oracle and Sybase(2) other relational databases, and (3) non-relational databases(including object oriented databases from Computer Associates, JYDSoftware Engineering, and Orient Technologies). Each of the customerservice, marketing, manufacturing, and engineering departments may havetheir own database or may share one or more databases. Each of the disksused to store databases is a non-volatile memory such as a hard disk oroptical disk. Alternatively, the databases may be stored in any storagedevice including solid state and/or semiconductor memory devices. As anexample, disk 64 contains the marketing database, disk 58 contains themanufacturing database, disk 70 contains the engineering database anddisk 76 contains the customer service database. Alternatively, the disks54 and 46 store one or more of the databases.

[0048] In addition to the workstations 56, 62, 68, 74 and 42 beingconnected to the WAN 10, these workstations may also include aconnection to a telephone line, ISDN, cable, or wireless network whichprovides a secure connection to the machine being monitored, diagnosedand/or controlled, and is used during communication. Additionally, ifone communication medium is not operating properly, one of the otherscan be automatically used for communication.

[0049] A feature of the present invention is the use of a“store-and-forward” mode of communication (e.g., Internet electronicmail, also referred to herein as e-mail) or transmission between amachine and a computer for diagnosing and controlling the machine.Alternatively, the message which is transmitted may be implemented usinga mode of communication that makes direct, end-to-end connections (e.g.,using a socket connection to the ultimate destination) such as FTP andHyper Text Transfer Protocol (HTTP).

[0050]FIG. 2 illustrates the mechanical layout of the digital imageforming apparatus 24 illustrated in FIG. 1. In FIG. 2, 101 is a fan forthe scanner, 102 is a polygonal mirror used with a laser printer, and103 designates an Fθ lens used to collimate light from a laser (notillustrated). Reference numeral 104 designates a sensor for detectinglight from the scanner. Reference numeral 105 designates a lens forfocusing light from the scanner onto the sensor 104, and referencenumeral 106 designates a quenching lamp used to erase images on thephotoconductive drum 132. There is a charging corona unit 107 and adeveloping roller 108. Reference numeral 109 designates a lamp used toillustrate a document to be scanned and 110, 111, and 112 designatemirrors used to reflect light onto the sensor 104. There is a drummirror 113 used to reflect light to the photoconductive drum 132originating from the polygon mirror 102. Reference numeral 114designates a fan used to cool the charging area of the digital imageforming apparatus, and reference numeral 115 designates a first paperfeed roller used for feeding paper from the first paper cassette 117,and reference numeral 116 designates a manual feed table. Similarly,reference numeral 118 designates a second paper feed roller for thesecond cassette 119. Reference numeral 120 designates a relay roller,121 designates a registration roller, 122 designates an image densitysensor, and 123 designates a transfer/separation corona unit. Referencenumeral 124 designates a cleaning unit, 125 designates a vacuum fan, 126designates a transport belt, 127 designates a pressure roller; and 128designates an exit roller. Reference numeral 129 designates a hot rollerused to fix toner onto the paper, 130 designates an exhaust fan and 131designates the main motor used to drive the digital image formingapparatus.

[0051]FIG. 3 is a block diagram illustrating the electronic componentsof the digital image forming apparatus of FIG. 2. The CPU 160 is amicroprocessor and acts as the system's controller. Random access memory(RAM) 162 stores dynamically changing information including operatingparameters of the digital image forming apparatus. A non-volatile memory(e.g., a read only memory 10 (ROM) 164 or a Flash Memory) stores (1) theprogram code used to run the digital image forming apparatus and (2)static-state data, describing the copier (e.g., the model number, serialnumber of the copier, and default parameters).

[0052] There is a multi-port network interface 166 which allows thedigital image forming apparatus to communicate with external devicesthrough at least one network. Reference number 168 represents atelephone, ISDN, or cable line, and numeral 170 represents another typeof network. Additional details of the multi-port network interface aredescribed with respect to FIG. 4. An interface controller 172 is used toconnect an operation panel 174 to a system bus 186. The operation panel174 includes standard input and output devices found on a digital imageforming apparatus including a copy button, keys to control the operationof the copier such as number of copies, reduction/enlargement,darkness/lightness, etc. Additionally, a liquid crystal display may beincluded within the operation panel 174 to display parameters andmessages of the digital image forming apparatus to a user.

[0053] A local connection interface 171 is a connection through localports such as RS232, the parallel printer port, USB, and IEEE 1394.FireWire (IEEE 1394) is described in Wickelgren, I., “The Facts About“FireWire”, IEEE Spectrum, April 1997, Vol. 34, Number 4, pp. 19-25, theentire contents of which are incorporated herein by reference.Preferably, a “reliable” communication protocol is used which includeserror detection and retransmission.

[0054] A storage interface 176 connects storage devices to the systembus 186. The storage devices include a flash memory 178, which can besubstituted by a conventional Electrically Erasable Programmable ReadOnly Memory (EEPROM), and a disk 182. The disk 182 includes a hard disk,optical disk, and/or a floppy disk drive. There is a connection 180connected to the storage interface 176 which allows for additionalmemory devices to be connected to the digital image forming apparatus.The flash memory 178 is used to store semi-static state data whichdescribes parameters of the digital image forming apparatus whichinfrequently change over the life of the copier. Such parameters includethe options and configuration of the digital image forming apparatus. Anoption interface 184 allows additional hardware such as an externalinterface to be connected to the digital image forming apparatus. Aclock/timer 187 is utilized to keep track of both the time and date andalso to measure elapsed time.

[0055] On the left side of FIG. 3, the various sections making up thedigital image forming device are illustrated. Reference numeral 202designates a sorter and contains sensors and

[0056] actuators used to sort the output of the digital image formingdevice. There is a duplexer 200 which allows a duplex operation to beperformed by the digital image forming device and includes conventionalsensors and actuators. The digital image forming device includes a largecapacity tray unit 198 which allows paper trays holding a large numberof sheets to be used with the digital image forming device. The largecapacity tray unit 198 includes conventional sensors and actuators.

[0057] A paper feed controller 196 is used to control the operation offeeding paper into and through the digital image forming device. Ascanner 194 is used to scan images into the digital image formingdevice-and includes conventional scanning elements such as a light,mirror, etc. Additionally, scanner sensors are used such as a homeposition sensor to determine that the scanner is in the home position,and a lamp thermistor is used to ensure proper operation of the scanninglamp. There is a printer/imager 192 which prints the output of thedigital image forming device, and includes a conventional laser printingmechanism, a toner sensor, and an image density sensor. The fuser 190 isused to fuse the toner onto the page using a high temperature roller andincludes an exit sensor, a thermistor to assure that the fuser 190 isnot overheating, and an oil sensor. Additionally, there is an optionalunit interface 188 used to connect to optional elements of the digitalimage forming device such as an automatic document feeder, a differenttype of sorter/collator, or other elements which can be added to thedigital image forming device.

[0058]FIG. 4 illustrates details of the multi-port network interface166. The digital image forming device may communicate to externaldevices through a token ring interface 220, a cable modem unit 222,which has a high speed connection over cable, a conventional telephoneinterface 224, which connects to a telephone line 168A, an ISDNinterface 226, which connects to an ISDN line 168B, a wireless interface228, or an ethernet interface 230, which connects to a LAN 170. Otherinterfaces may include, but are not limited to, a Digital SubscriberLine (DSL) (original DSL, concentric DSL, and asymmetric DSL). A singledevice which connects to both a Local Area Network and a telephone lineis commercially available from Megahertz and is known as theEthernet-Modem.

[0059] The CPU or other microprocessor or circuitry executes amonitoring process to monitor the state of each of the sensors of thedigital image forming device, and a sequencing process is used toexecute the instructions of the code used to control and operate thedigital image forming device. Additionally, there is (1) a centralsystem control process executed to control the overall operation of thedigital image forming device, and (2) a communication process used toassure reliable communication to external devices connected to thedigital image forming device. The system control process monitors andcontrols data storage in a static state memory (e.g., the ROM 164 ofFIG. 3), a semi-static memory (e.g., the flash memory 178 or disk 182),or the dynamic state memory (e.g., a volatile or non-volatile memory(e.g., the RAM 162 or the flash memory 178 or disk 182). Additionally,the static state memory may be a device other than the ROM 164 such as anon-volatile memory including either of the flash memory 178 or disk182.

[0060] The above details have been described with respect to a digitalimage forming device, but the present invention is equally applicable toother business office machines or devices such as an analog copier, afacsimile machine, a scanner, a printer, a facsimile server, or otherbusiness office machines, a business office appliance, or otherappliances (e.g., a microwave oven, VCR, digital camera, cellular phone,palm top computer). Additionally, the present invention includes othertypes of devices which operate using store-and-forward or directconnection-based communication. Such devices include metering systems(including gas, water, or electricity metering systems), vendingmachines, or any mechanical device (e.g., automobiles) that needs to bemonitored during operation or remote diagnosis. In addition tomonitoring special purpose machines and computers, the invention can beused to monitor, control, and diagnose a general purpose computer thatwould be the monitored and/or controlled device.

[0061]FIG. 5 illustrates an alternative system diagram of the presentinvention in which different devices and subsystems are connected to theWAN 10. However, there is no requirement to have each of these devicesor subsystems as part of the invention. Each component or subsystemillustrated in FIG. 5 is individually part of the invention. Further,the elements illustrated in FIG. 1 may be connected to the WAN 10 whichis illustrated in FIG. 5. In FIG. 5, there is illustrated a firewall50-1 connected to an intranet 260-1. A service machine 254 connected tothe intranet 260-1 includes therein, or has connected thereto, data 256that may be stored in a database format. The data 256 includes history,performance, malfunction, and any other information such as statisticalinformation of the operation or failure or set-up the monitored devices,or configuration information such as which components or optionalequipment is included with the monitored devices. The service machine254 may be implemented as the device or computer which requests themonitored devices to transmit data, or which requests that remotecontrol and/or diagnostic tests be performed on the monitored devices.The service machine 254 may be implemented as any type of device, and ispreferably implemented using a computerized device such as a generalpurpose computer.

[0062] Another sub-system of FIG. 5 includes a firewall 50-2, anintranet 260-2, and a printer 262 connected thereto. In this sub-system,the functions of sending and receiving electronic messages by theprinter 262 (and similarly by a copier 286) are performed by (1)circuitry, (2) a microprocessor, or (3) any other type of hardwarecontained within or mounted to the printer 262 (i.e., without using aseparate general purpose computer).

[0063] An alternate type of sub-system includes the use of an InternetService Provider 264 which may be any type of Internet Service Provider(ISP), including known commercial companies such as America Online,Earthlink, and Niftyserve. In this sub-system, a computer 266 isconnected to the ISP 264 through a digital or analog modem (e.g., atelephone line modem, a cable modem, modems which use any type of wiressuch as modems used over an Integrated Services Digital Network (ISDN)line or an Asymmetric Digital Subscriber Line (ADSL), modems which useframe relay communication, wireless modems such as a radio frequencymodem, a fiber optic modem, or a device which uses infrared lightwaves). Further, a business office device 268 is connected to thecomputer 266. As an alternative to the business office device 268 (orany other device illustrated in FIG. 5), a different type of machine maybe monitored or controlled such as a digital copier, any type ofappliance, security system, or utility meter, such as an electrical,water, or gas utility meter, or any other device discussed herein.

[0064] Also illustrated in FIG. 5 is a firewall 50-3 connected to anetwork 274. The network 274 may be implemented as any type of computernetwork, (e.g., an ethernet or token ring network). Networking softwarewhich may be used to control the network includes any desired networkingsoftware including software commercially available from Novell orMicrosoft. The network 274 may be implemented as an intranet, ifdesired. A computer 272 connected to the network 274 may be used toobtain information from a business office device 278 and generatereports such as reports showing problems that occurred in variousmachines connected to the network, and a monthly usage report of thedevices connected to the network 274. In this embodiment, a computer 276is connected between the business office device 278 and the network 274.This computer receives communications from the network and forwards theappropriate commands or data, or any other information, to the businessoffice device 278. Communication between the business office device 278and the computer 276 may be accomplished using wire-based or wirelessmethods including, but not limited to, radio frequency connections,electrical connections and light connections (e.g., an infraredconnection, or a fiber optics connection). Similarly, each of thevarious networks and intranets illustrated in FIG. 5 may be establishedusing any desired manner including through the establishment of wirelessnetworks such as radio frequency networks. The wireless communicationdescribed herein may be established using spread spectrum techniquesincluding techniques which use a spreading code and frequency hoppingtechniques such as the frequency hopping wireless technique which isdisclosed in the Bluetooth Specification LOA (available at the WorldWide Web site www.bluetooth.com), which is incorporated herein byreference.

[0065] Another sub-system illustrated in FIG. 5 includes a firewall50-4, an intranet 260-4, a computer 282 connected thereto, a businessoffice appliance 285 and a copier 286. The computer 282 may be used togenerate reports and request diagnostic or control procedures. Thesediagnostic and control procedures may be performed with respect to thebusiness office appliance 285 and the copier 286 or any of the otherdevices illustrated in or used with FIG. 5. While FIG. 5 illustrates aplurality of firewalls, the firewalls are preferable, but optionalequipment, and therefore, the invention may be operated without the useof firewalls, if desired.

[0066]FIG. 6A illustrates a device/appliance 300 connected to a typicale-mail exchange system which includes components 302, 304, 306,308, 310,312, 314, 316, and 318, which may be implemented in a conventionalmanner, and are adapted from FIG. 28.1 of Stevens, above. A computerinterface 302 interfaces with any of the application units ordevices/appliances 300 described herein. While FIG. 6A illustrates thatthe device/appliance 300 is the sender, the sending and receivingfunctions may be reversed in FIG. 6A. Furthermore, if desired, the usermay not be needed to interface with the device/appliance 300 at all. Thecomputer interface 302 then interacts with a mail agent 304. Popularmail agents for Unix include MH, Berkeley Mail, Elm, and Mush. Mailagents for the Windows family of operating systems include MicrosoftOutlook and Microsoft Outlook Express. At the request of the computerinterface 302, the mail agent 304 creates e-mail messages to be sentand, if desired, places these messages to be sent in a queue 306. Themail to be sent is forwarded to a Message Transfer Agent (MTA) 308. Acommon MTA for Unix systems is Sendmail. Typically, the message transferagents 308 and 312 exchange communications using a TCP/IP connection310. Notably, the communication between the message transfer agents 308and 312 may occur over any size network (e.g., WAN or LAN). Further, themessage transfer agents 308 and 312 may use any communication protocol.In one embodiment of the present invention, elements 302 and 304 of FIG.6A reside in the library to monitor the usage of the application unit.

[0067] From the message transfer agent 312, e-mail messages are storedin user mailboxes 314 which are transferred to the mail agent 316 andultimately transmitted to the user at a terminal 318 which functions asa receiving terminal.

[0068] This “store-and-forward” process relieves the sending mail agent304 from having to wait until a direct connection is established withthe mail recipient. Because of network delays, the communication couldrequire a substantial amount of time during which the application wouldbe unresponsive. Such an unresponsiveness is generally unacceptable tousers of the application unit. By using e-mail as the store-and-forwardprocess, retransmission attempts after failures occur automatically fora fixed period of time (e.g., three days). In an alternate embodiment,the application can avoid waiting by passing communicating requests toone or more separate threads. Those threads can then controlcommunication with the receiving terminal 318 while the applicationbegins responding to the user interface again. In yet another embodimentin which a user wishes to have communication completed beforecontinuing, direct communication with the receiving terminal is used.Such direct communication can utilize any protocol not blocked by afirewall between the sending and receiving terminals. Examples of suchprotocols include File Transfer Protocol (FTP) and Hyper Text TransferProtocol (HTTP).

[0069] Public WANs, such as the Internet, are generally not consideredto be secure. Therefore, if it is desired to keep messages confidential,messages transmitted over the public WANs (and multi-company privateWANs) can be encrypted. Encryption mechanisms are known and commerciallyavailable which may be used with the present invention. For example, aC++ library function, crypt( ), is available from Sun Microsystems foruse with the Unix operating system. Other encryption and decryptionsoftware packages are known and commercially available and may also beused with this invention. One such package is PGP Virtual PrivateNetwork (VPN) available from Network Associates. Other VPN software isavailable from Microsoft Corporation.

[0070] As an alternative to the general structure of FIG. 6A, a singlecomputer may be used which functions as the computer interface 302, themail agent 304, the mail queue 306 and the message transfer agent 308.As illustrated in FIG. 6B, the device/appliance 300 is connected to acomputer 301 which includes the message transfer agent 308.

[0071] A further alternative structure is shown in FIG. 6C in which themessage transfer agent 308 is formed as part of the device/appliance300. Further, the message transfer agent 308 is connected to the messagetransfer agent 312 by a TCP/IP connection 310. In the embodiment of FIG.6C, the device/appliance 300 is directly connected to the TCP/IPconnection 310 with an e-mail capability. One use of the embodiment ofFIG. 6C includes using a facsimile machine with an e-mail capability(e.g., as defined in RFC 2305 (a simple mode of facsimile using Internetmail)) as the device/appliance 300.

[0072]FIG. 6D illustrates a system in which a device/appliance 300 doesnot by itself have the capability to directly receive e-mail, but has aconnection 310 to a mail server/POP3 server including a message transferagent 308 and a mail box 314 so that the device/appliance 300 uses thePOP3 protocol to retrieve received mail from the mail server.

[0073]FIG. 7 illustrates an alternative implementation of transferringmail and is adapted from FIG. 28.3 of Stevens referenced previously.FIG. 7 illustrates an electronic mail system having a relay system ateach end. The arrangement of FIG. 7 allows one system at an organizationto act as a mail hub. In FIG. 7, there are four MTAs connected betweenthe two mail agents 304 and 316. These MTAs include local MTA 322A,relay MTA 328A, relay MTA 328B, and local MTA 322D. The most commonprotocol used for mail messages is SMTP (Simple Mail Transfer Protocol)which may be used with this invention, although any desired mailprotocol may be utilized. In FIG. 7, 320 designates a sending host whichincludes the computer interface 302, the mail agent 304, and the localMTA 322A. The device/appliance 300 is connected to, or alternativelyincluded within, the sending host 320. As another case, thedevice/appliance 300 and host 320 can be in one machine where the hostcapability is built into the device/appliance 300. Other local MTAs322B, 322C, 322E and 322E may also be included. Mail to be transmittedand received may be queued in a queue of mail 306B of the relay MTA328A. The messages are transferred across the TCP/IP connection 310(e.g., an Internet connection or a connection across any other type ofnetwork).

[0074] The transmitted messages are received by the relay MTA 328B andif desired, stored in a queue of mail 306C. The mail is then forwardedto the local MTA 322D of a receiving host 342. The mail may be placed inone or more of the user mailboxes 314 and subsequently forwarded to themail agent 316, and finally forwarded to the user at a terminal 318. Ifdesired, the mail may be directly forwarded to the terminal without userinteraction.

[0075] The various computers used in the present invention, includingthe computers 266 and 276 of FIG. 5, may be implemented as illustratedin FIG. 8. Further, any other computer used in this invention may beimplemented in a similar manner to the computer illustrated in FIG. 8,if desired, including the service machine 254, computer 272, andcomputer 282 of FIG. 5. However, not every element illustrated in FIG. 8is required in each of those computers.

[0076] In FIG. 8, the computer 360 includes a CPU 362 which may beimplemented as any type of processor including commercially availablemicroprocessors from companies such as Intel, AMD, Motorola, Hitachi andNEC. There is a working memory such as a RAM 364, and a wirelessinterface 366 which communicates with a wireless device 368. Thecommunication between the interface 366 and device 368 may use anywireless medium (e.g., radio waves or light waves). The radio waves maybe implemented using a spread spectrum technique such as Code DivisionMultiple Access (CDMA) communication or using a frequency hoppingtechnique such as that disclosed in the Bluetooth specification.

[0077] There is a ROM 370 and a flash memory 371, although any othertype of non-volatile memory (e.g., Erasable Programable ROM, or anEEPROM) may be used in addition to or in place of the flash memory 371.An input controller 372 has connected thereto a keyboard 374 and a mouse376. There is a serial interface 378 connected to a serial device 380.Additionally, a parallel interface 382 is connected to a parallel device384, a universal serial bus (USB) interface 386 is connected to auniversal serial bus device 388, and also there is an IEEE 1394 device400, commonly referred to as a fire wire device, connected to an IEEE1394 interface 398. The various elements of the computer 360 areconnected by a system bus 390. A disk controller 396 is connected to afloppy disk drive 394 and a hard disk drive 392. A communicationcontroller 400 allows the computer 360 to communicate with othercomputers (e.g., by sending e-mail messages) over a telephone line 402or a network 404. An I/O (Input/Output) controller 408 is connected to aprinter 410 and a hard disk 412, for example using a SCSI (SmallComputer System Interface) bus. There is also a display controller 416connected to a CRT (Cathode Ray Tube) 414, although any other type ofdisplay may be used including a liquid crystal display, a light emittingdiode display, a plasma display, etc.

[0078]FIG. 9 illustrates an application of the present invention.Devices 901, 903, 905 and 907 that are connected to the Intranet 910 arethe devices to be monitored locally by a remote monitoring workstation911 with its database 913. Alternatively, the remote monitoringworkstation 911 can function to send the device status information tothe central monitoring workstation 945 by polling the information fromthe monitored devices 901, 903, 905, and 907 and by sending theinformation through the firewall 917. The remote monitoring workstation911, therefore, can function either as a monitoring device or as acommunication and administrative device between the monitored devicesand monitoring device. In FIG. 9, the remote monitoring workstation 911uses the Simple Network Management Protocol (SNMP) defined by IETF tocommunicate with the attached devices. SNMP is described in “ManagingInternetworks with SNMP, third edition” by Mark A. Miller, P. E., M & TBook, 1999. The entire contents of this reference are incorporatedherein by reference. If some of the devices to be monitored do notsupport SNMP, the remote monitoring workstation 911 can use a differentmethod to obtain the necessary information. After obtaining thenecessary information, the remote monitoring workstation 911 uses theSimple Mail Transfer Protocol (SMTP) Server 915 to send out thenecessary information to the central monitoring workstation 945 throughthe Mail Server 943 that supports the Post Office Protocol Version 3(POP3) (IETF Networking Group Request For Comments [RFC]: 1939). Theremote monitoring workstation 911 uses SMTP (SMTP is defined in IETF RFC821) and possibly Multipurpose Internet Mail Extensions (MIME) to sende-mails. The remote monitoring workstation 911 generates the mailmessage that is at and above the Application Layer of the TCP/IP modelor the ISO seven-layer model, as shown later. Alternatively, the remotemonitoring workstation 911 may include an SMTP processor to send out thenecessary information using e-mail.

[0079] The LAN 920 and intranet 930 send similar information to thecentral monitoring workstation 945. When the e-mails that contain themonitoring information of devices arrive at the firewall 941 of theintranet 950, the mail is routed to the Mail Server 943 with POP3. Thecentral monitoring workstation 945 periodically accesses the Mail Server943 to obtain the arrived e-mail, parse the mail and its content viaPOP3 and stores the necessary information in the database 947. Thedatabase 949 contains the additional information of the monitored devicecharacteristics and history. The computers 951 and 953 perform theanalysis of obtained data to take the necessary actions. Alternatively,the central monitoring workstation 945 may contain a mail receivingcapability, and the firewall may route the e-mail directly to thecentral monitoring workstation 945.

[0080]FIGS. 10A and 10B illustrate an overall software architecture ofthe system shown in FIG. 9 according to one embodiment of the presentinvention. FIG. 10A illustrates the architecture of the software used bythe networks that send the e-mails with the information on the monitoreddevices in FIG. 9 according to one embodiment of the present invention.The Sender Service 1001 module is the system resident software that setsup the destination for the monitored information to be sent, initiatesthe sending of the configuration and contact information to thedestination, and periodically monitors and sends the information to thedestination by using the three functions defined in 1000 (i.e.,setDestination, obtainAndUpdateStatus, and sendConfig) to trigger thesend module, Monitor_Send DLL 1003. The Monitor_Send DLL 1003 moduleuses two other modules, the Database 1005 module to store the deviceinformation and device-related information along with the monitoredinformation that is stored until it is sent out, and the SNMP++ DLL 1007module that is used to obtain the information from the devices.

[0081]FIG. 10B illustrates the architecture of the software used by thereceiving side (e.g., intranet 950) in FIG. 9 according to oneembodiment of the present invention. The Receiver Service 1011 module isthe system resident software that sets up access to the mail serverwhere the monitored information is to be sent, and periodically obtainsthe monitored information from the mail server through the two functionsdefined in 1010 (i.e., setupPOP3Server, and getMailAndUpdateDatabase) totrigger the Receive_Store DLL 1013 module. The Receive_Store DLL 1013module uses two other modules, the Database 1017 module to store deviceinformation and device-related information along with the monitoredinformation and the POP3 1015 module to retrieve information from themail server.

[0082]FIG. 11 illustrates the general architecture of the Monitor_SendDLL 1003 module according to one embodiment of the present invention.This part of the system is responsible for monitoring the status of thedevices and for sending e-mails containing status and configurationinformation of the monitored devices. The Interface 1101 module allowsany application to use the Monitor_Send DLL 1003 module. For example,the Sender Service 1001 module in FIG. 10A accesses the Monitor_Send DLL1003 module through the Interface 1101 module. The Device Information1105 module is responsible for obtaining configuration information fromthe monitored devices and initiating the sending of the configurationinformation. The Device Monitor 1103 module is responsible for obtainingstatus information from the monitored devices and initiating the sendingof the status information. The Data Transfer 1107 module is responsiblefor providing a method through which the status and configurationinformation is sent. The ODBC Interface 1109 module provides a method toaccess and store information in a database. Each of the components ofthe Monitor_Send DLL 1003 module provides interface functions that allowthem to perform its tasks. For example, the functions of the DataTransfer 1107 module are provided through four interface functions,setDestination, startSend, dataSend, and endSend.

[0083]FIG. 12 illustrates a general architecture of the Receive_StoreDLL 1013 module according to one embodiment of the present invention.This part of the system is responsible for retrieving the informationthat was sent to it by the Monitor_Send DLL 1003 module and storing theinformation in the database. The Interface 1101 module allows anyapplication to use the Receive_Store DLL 1013 module. For example, theReceiver Service 1011 module in FIG. 10B accesses the Receive_Store DLL1013 module through the Interface 1101 module. The Receive Manager 1203module is responsible for obtaining the configuration information andstatus information of the monitored devices from the POP3 server andstoring that information in the database. The Data Retriever 1205 moduleis responsible for retrieving the data from the POP3 server. The POP3Processor 1207 module is responsible for accessing the information sentto it by the Monitor_Send DLL 1003 module. The Parser 1211 module isresponsible for parsing the information obtained from the POP3 server.The ODBC Interface 1109 module is responsible for storing theinformation sent to it in a database. Each of the components of theReceive_Store DLL 1013 module provides interface functions that allowthem to perform its tasks.

[0084]FIG. 13A is a flowchart providing an overview of the functionsperformed by the Device Information 1105 module in the context of thesystem diagram of FIG. 9. This process focuses on the sending ofconfiguration information of the monitored devices from the remotemonitoring workstation 911 to the central monitoring workstation 945,and not the sending of status information, which is described below inthe context of the Device Monitor 1103 module. Configuration informationfor the monitored devices maintained by the central monitor may beeither originally sent, or updated, through the functions performed bythe Device Information 1105 module, as will be understood in light ofthe description provided herein.

[0085] As shown in FIG. 13A, the process begins with step S1301 wherethe database 913 is queried by the remote monitoring workstation 911 toobtain configuration information and IP address informationcorresponding to the devices being monitored by that particular remotemonitoring workstation 911. The process then proceeds to step S1302where, using the IP address obtained from the database 913, the remotemonitoring workstation 911 queries the individual monitored devicesusing SNMP commands to obtain a device-unique identifier (e.g., a MACaddress) for each of the devices being monitored. The process thenproceeds to step S1303 where the remote monitoring workstation 911stores the device-unique identifier in the database. The process thenproceeds to step S1304 where the configuration information, includingthe IP address obtained from the database 913 and the device-uniqueidentifier obtained through SNMP commands, are formatted into a commonmap structure. The process then proceeds to step S1305 where theconfiguration information including the device-unique identifier is sentto the central monitoring workstation 945 via an e-mail message throughthe SMTP server 915. Once the information has been sent, the processends.

[0086]FIG. 13B is a class diagram illustrating one embodiment of theDevice Information 1105 module of FIG. 11 according to the presentinvention. The Device Information 1105 module is responsible fortriggering the Data Transfer 1107 module to start the sending ofconfiguration information, obtaining the device configurationinformation from the database 913 via the ODBC Interface 1109 module,obtaining a device-unique identifier (e.g., a MAC address) from themonitored SNMP devices and updating the device configuration informationin the database 913 to include the device-unique identifier, formattingthe device configuration information into a map structure, sending themap structure to the Data Transfer 1107 module, and completing thesending of the configuration information via the Data Transfer 1107module.

[0087] The database 913 is not initially populated with a device-uniqueidentifier for the monitored devices. The Device Information 1105 moduleis responsible for obtaining this information from the monitored devicesbased on information that is originally stored in the database (e.g,. IPaddress information), via SNMP commands. The device-unique identifier,obtained directly from the devices, is then populated by the DeviceInformation 1105 module into the database 913.

[0088] The map structure used in storing the information to be sent fromthe remote monitoring workstation 911 to the central monitoringworkstation 945 is a standard structure for storing key/value data. Eachentry in the map includes a key indicating what the data represents, anda data field containing the value of the data. In one embodiment of thepresent invention, the key of the map is a string or a number associatedwith a particular data field, and the data field is a string value. Mapstructures are included with the standard C++ language, and similarstructures, sometimes called a dictionary structure, are included withother standard languages. An example of a populated map structure isshown below as Table 1: TABLE 1 Example Map Structure IncludingConfiguration Information Key Value (Data) “Manufacturer” (or 100)“Xerox” “Model” (or 101) “DocuPrint N4025” “SerialNumber” (or 102)“PF4-027955” “MACAddress” (or 103) “00 00 AA 79 07 76” “IPAddress” (or104) “172.30.4.53” “CompanyName” (or 105) “Ricoh Corporation” “Street”(or 106) “1996 Lundy Ave” “City” (or 107) “San Jose” “State” (or 108)“CA” “ZipCode” (or 109) “95131” “Location” (or 110) “Lab”“ContactPerson” (or 111) “John Smith” “PhoneNumber” (or 112)“4085551212”

[0089] The Device Information 1105 module contains two classes,CDeviceInformation 1301 and CIP_MACmap 1303. The CDeviceInformation 1301class is responsible for obtaining the configuration information fromthe database 913, and initiating the sending of the information throughe-mail from the remote monitoring workstation 911 to the centralmonitoring workstation 945. The CDeviceInformation 1301 class interactswith the database 913 via the ODBC Interface 1109 module to obtain theconfiguration information, and uses the Data Transfer 1107 module totransmit the configuration information to the central monitoringworkstation 945.

[0090] The CIP_MACmap 1303 class makes use of the CSnmpResource 1305class to obtain a physical address (e.g., a MAC address) from themonitored SNMP devices. The MAC address is used to uniquely identify themonitored devices within the database 947 maintained by, for example,the central monitoring workstation 945. While an IP address, forexample, may uniquely identify a monitored device among the devicesconnected to a particular network monitored by the remote monitoringworkstation 911, that address may not be unique among all of thenetworks being monitored by the central monitoring workstation 945. Itis for this reason that, in this example, a MAC address is used toprovide a globally unique identification for a particular device thatcan be relied on by the central monitoring workstation 945.

[0091] If other device-unique identification is available, the classstructure shown in FIG. 13B can be modified to accommodate that uniqueidentification.

[0092]FIG. 14 is a collaboration diagram illustrating the interactionamong the classes of the Device Information 1105 module shown in FIG.13B to obtain and send configuration information of a monitored devicefrom the remote monitoring workstation 911 to the central monitoringworkstation 945. As shown in FIG. 14, the process is initiated by a callto the sendConfig( ) method of the CDeviceInformation 1403 class by theInterface 1101. In response, the CDeviceInformation 1403 class calls thestartSend( ) method of the CDataTransfer 1405 class to initiate acommunication link for sending of the e-mail message that will containthe configuration information. The CDeviceInformation 1403 class thencalls the getDeviceInformation( ) method of the CSendODBCInterface 1411class to obtain the configuration information, including the IP address,of the monitored device from the database. The CDeviceInformation 1403class then calls the getMACforIP( ) method of the CIP_MACmap 1407 classto obtain a physical address (e.g., the MAC address) for the monitoreddevices based on the IP address that was obtained from the database. Inturn, the CIP_MACmap 1407 class calls the setIPAddressOfAgent( ) andgetOctetStringValueForOID( ) methods of the CSnmpResource 1409 class toquery the monitored device based on its IP address to receive itsphysical address through the appropriate SNMP functions. Next, theCDeviceInformation 1403 class calls the setDeviceInformation( ) methodof the CSendODBCInterface 1411 class to store the configurationinformation in the database.

[0093] The CDeviceInformation 1403 class then calls the dataSend( )method of the CDataTransfer 1405 class to send the configurationinformation, along with the physical address information, to the centralmonitoring workstation 945. Finally, the CDeviceInformation 1403 classcalls the endSend( ) method of the CDataTransfer 1405 class to completethe sending of the configuration information.

[0094]FIG. 15A is a flowchart providing an overview of the functionsperformed by the Device Monitor 1103 module in the context of the systemdiagram of FIG. 9. This process focuses on the collection, storing, andsending of information of the monitored devices from the remotemonitoring workstation 911 to the central monitoring workstation 945 asan e-mail message via the SMTP server 915.

[0095] As shown in FIG. 15A, the process begins with step S1501 where itis determined whether information is to be sent to the centralmonitoring workstation 945. In one embodiment of the present invention,some information is sent from the remote monitoring workstation 911 tothe central monitoring workstation 945 at a different frequency (e.g.,less frequently) than a frequency that the monitored devices are polledfor status. If it is determined that the collected information is not tobe sent to the central monitoring workstation 945 (i.e., “NO” at stepS1501), the process proceeds to step S1502 where the monitored devicesare polled for a first type of information only.

[0096] The first type of information may include, for example, certainstatus information that may change states more frequently thaninformation is reported to the central monitoring workstation. A secondtype of information may include a different class of status information,for example, a counter, a level indicator, or a configuration setting ofa monitored device. For this second type of information, interim valuesbetween reporting periods are not of interest. As would be understood,it is quite possible that, depending on the frequency with whichinformation is sent to the central monitoring workstation 945, statusinformation corresponding to the first type of information, for example,an error condition, could have been corrected between transmissions tothe central monitoring workstation 945. For that reason, it is helpfulto store the first type of information, so that when information is sentto the central monitoring workstation 945, it can be reported that, inthis example, a particular error condition, while not necessarily stillpresent, had occurred since the last time information was sent.Accordingly, when the information, including both the first type and thesecond type of information, is sent to the central monitoringworkstation 945, the first type of information stored in the database913 is queried from the database 913 and sent along with the most recentinformation. Then, those values in the database 913 are reset to clearany information that had been stored leading up to the transmission tothe central monitoring workstation 945.

[0097] Returning to FIG. 15A, once the first type of information hasbeen collected from the network device, the process proceeds to stepS1503 where the first type of information is stored in the database 913by the remote monitoring workstation 911. After the first type ofinformation is stored in the database 913, the process ends.

[0098] If, on the other hand, it is determined that information is to besent to the central monitoring workstation 945 (i.e., “YES” at stepS1501), the process proceeds to step S1504 where the monitored devicesare polled for both the first type of information and the second type ofinformation. Once this information is obtained, the process proceeds tostep S1505 where the database is queried for the stored first type ofinformation previously collected. The process then proceeds to stepS1506 where both the first type and the second type of information justcollected, as well as the first type of information retrieved from thedatabase, is formatted into a common map structure. This is the same mapstructure that was used by the Device Information 1105 module to sendthe configuration information. The process then proceeds to step S1507where both the first type and second type of information is sent by theremote monitoring workstation 911 to the central monitoring workstation945 as an e-mail message via the SMTP server 915. After the statusinformation has been sent by the remote monitoring workstation 911, theprocess proceeds to step S1508 where, as discussed above, the remotemonitoring workstation 911 resets the values corresponding to the firsttype of information stored in the database 913 to clear any conditionsthat may have been recorded leading up to the sending of theinformation. Once the database 913 values arereset, the process ends.

[0099]FIG. 15B is a class diagram illustrating one embodiment of theDevice Monitor 1103 module of FIG. 11 according to the presentinvention. The Device Monitor 1103 module is responsible for logging andmaintaining information about the network devices. This Device Monitor1103 module is also responsible for ensuring that the information issent to the central monitoring workstation 945. If the information isnot to be sent upon being collected, the Device Monitor 1103 moduleobtains and stores only certain types of information (e.g., occurrenceof no toner, door open, jam, etc.) in the database 913. If theinformation is to be sent upon being collected, the Device Monitor 1103module obtains other types of information, including, for example, lessvolatile status information. The Device Monitor 1103 module includesthree classes, CDeviceStatusMonitorAndSendManager 1601,CDeviceStatusLogger 1603, and CSnmpResource 1607.

[0100] The CDeviceStatusMonitorAndSendManager 1601 class is responsiblefor obtaining the information from the monitored devices and sending theinformation to the central monitoring workstation 945. TheCDeviceStatusMonitorAndSendManager 1601 class uses the Data Transfer1107 module discussed above to send the information to the centralmonitoring workstation 945.

[0101] The CDeviceStatusLogger 1603 class is responsible for logging andmaintaining the information of the monitored devices. TheCDeviceStatusLogger 1603 class obtains and stores information of themonitored devices in the database 913 using the ODBC Interface 1109module discussed above. The CDeviceStatusLogger 1603 class includes theDevicePerStatus structure for storing the first type of information ofthe monitored devices in the database 913. In one embodiment of thepresent invention, only this first type of information is stored in thedatabase.

[0102] The CSnmpResource 1607 class is responsible for providing thenetwork management protocol (e.g., SNMP) which provides the capabilityfor collecting the information from the monitored devices. TheCSnmpResource 1607 class uses the SNMP++ DLL 1609 to implement theSimple Network Management Protocol to gather the information from themonitored devices.

[0103]FIG. 16 is a collaboration diagram illustrating the interactionamong the classes of the Device Monitor 1103 module to obtain and storethe first type of information from the monitored devices. As discussedabove, if the information collected from the monitored devices is not tobe sent to the central monitoring workstation 945 upon collection, onlythis first type of information is collected and stored in the database913. As shown in FIG. 16, the process is initiated by theCDeviceStatusMonitorAndSendManager 1601 class invoking thelogDevicePerStatus( ) method of the CDeviceStatusLogger 1603 class toinitiate the collection and storing of the first type of information ofthe monitored devices. The CDeviceStatusLogger 1603 class then calls thegetDevicePerStatus( ) method of the ODBC Interface 1109 module to obtainthe latest information of the monitored devices, including the IPaddresses of the devices, from the database 913. Next, theCDeviceStatusLogger 1603 class calls the setIPAddressOfAgent( ) methodof the CSnmpResource 1607 class which, in turn, calls the set_address( )method of the SNMP++ DLL 1609 to establish an IP address of a devicefrom which the first type of information is to be collected. Next, theCDeviceStatusLogger 1603 class calls the getOctetStringValueForOID( )method of the CSnmpResource 1607 class which, in turn, calls the get( )method and the get-value( ) method of the SNMP++ DLL 1609 to obtain thelatest information of the monitored devices via SNMP using the IPaddress of the device. Once the information has been returned, theCDeviceStatusLogger 1603 class calls the setDevicePerStatus( ) method ofthe ODBC Interface 1109 module to store the information of the monitoreddevices in the database 913 using the DevicePerStatus 1505 structure.

[0104]FIG. 17 is a collaboration diagram illustrating the interactionamong the classes of the Device Monitor 1103 module to obtain both afirst type and a second type of information from the monitored devicesand to reset the values corresponding to the first type of informationstored in the database 913 for each monitored device. As discussedabove, if the information collected from the monitored devices is to besent to the central monitoring workstation 945 upon collection, both thefirst type of information and the second type of information iscollected. As shown in FIG. 17, the process is initiated by theCDeviceStatusMonitorAndSendManager 1601 class invoking thegetNextDeviceStatus( ) method of the CDeviceStatusLogger 1603 class toinitiate the collection of the information (both the first type, and thesecond type of information) of the monitored devices. Steps 2-8 incollecting both types of information are the same as steps 2-8 describedabove (i.e., the calls to getDevicePerStatus( ), setIPAddressOfAgent( ),set_Address( ), getOctetStringValueForOID( ), get( ), get_value( ), andsetDevicePerStatus( )) in the context of FIG. 16 for collecting only thefirst type of information. However, the call to the setDevicePerStatus() method of the ODBC Interface 1109 module in this case (i.e., step 8)is used to reset the values corresponding to the first type ofinformation stored in the database.

[0105] After resetting the values in the database, theCDeviceStatusLogger 1603 class calls the getStringValueForOID( ) methodof the CSnmpResource 1607 class which, in turn, calls the get( ) andget_printable_value( ) methods of the SNMP++ DLL 1609 module to obtainthe second type of information from the monitored devices via SNMPcommands.

[0106]FIG. 18 is a collaboration diagram illustrating the interactionamong the classes of the Device Monitor 1103 module to send both thefirst type and second type of information of the monitored devices tothe central monitoring workstation 945. As shown in FIG. 18, the processis initiated by the CDeviceStatusMonitorAndSendManager 1601 classinvoking the getNextDeviceStatus( ) method of the CDeviceStatusLogger1603 class to obtain the information of the monitored devices asdiscussed above in the context of FIG. 17. Next, theCDeviceStatusMonitorAndSendManager 1601 class calls the startSend( ) anddataSend( ) methods of the Data Transfer 1107 module to initiate thesending of the information to the central monitoring workstation 945.Then, the CDeviceStatusMonitorAndSendManager 1601 class iterativelycalls the getNextDeviceStatus( ) method of the CDeviceStatusLogger 1603class to obtain information from a monitored device, followed by a callto the dataSend( ) method of the CDataTransfer 1405 class, shown in FIG.19C, of the Data Transfer 1107 module to send the information for aparticular monitored device to the central monitoring workstation 945.Once information has been sent for all of the monitored devices, theCDeviceStatusMonitorAndSendManager 1601 class calls the endSend( )method of the CDataTransfer 1405 class, shown in FIG. 19C, of the DataTransfer 1107 module to complete the sending of the information.

[0107]FIG. 19A is a flowchart providing an overview of the functionsperformed by the Data Transfer 1107 module in the context of the systemdiagram of FIG. 9. This process focuses on the Data Transfer 1107 moduleresponsible for sending the configuration and status information, andnot the collection of the configuration and status information to besent, as is described above in the context of the Device Information1105 module and the Device Monitor 1103 module, respectively.

[0108] As shown in FIG. 19A, the process begins with step S1901 wherethe system registry of the remote monitoring workstation 911 ispopulated with a source address and a destination address for e-mailstransferring status information of the monitored devices. In thisexample, the source address will be the e-mail address of the remotemonitoring workstation 911, and the destination address will be thee-mail address of the central monitoring workstation 945. Once thesource and destination addresses have been populated in the systemregistry of the remote monitoring workstation 911, the transfer ofinformation may begin.

[0109] The process then proceeds to step S1902 where a transfer ofinformation commences. In step S1902, the remote monitoring workstation911 accesses its system registry to obtain source and destination e-mailaddress information that will be used to populate header information foran e-mail message originating from the remote monitoring workstation 911and having a destination of the central monitoring workstation 945.

[0110] Once the source and destination information has been obtained,the process proceeds to step S1903 where a communication link isestablished between the remote monitor workstation 911 and a Simple MailTransfer Protocol (SMTP) Server 915. Once the communication link hasbeen established, the process proceeds to step S1904, where theconfiguration or status information is sent as an e-mail message fromthe remote monitoring workstation 911 to the SMTP server 915 via thecommunication link. The SMTP server 915 will route the e-mail message tothe appropriate recipient, in this case, the central monitoringworkstation 945. In one embodiment of the present invention, the remotemonitoring workstation 911 sends the configuration or status informationas a Multipurpose Internet Mail Extensions (MIME) attachment to theInternet e-mail message. As discussed above, the configuration or statusinformation, prior to sending it to the central monitoring workstation945, is maintained in the database 913. Once the configuration or statusinformation has been sent, the process proceeds to step S1905, where theremote monitoring workstation 911 will shut down the communication linkbetween itself and the SMTP Server 915. Once the communication link hasbeen shut down, the process ends.

[0111]FIG. 19B is a flowchart describing in further detail theprocessing performed in sending configuration or status information asan attachment to an e-mail message (e.g., the process performed in stepS1904 of FIG. 19A) according to one embodiment of the present invention.As shown in FIG. 19B, the sending the configuration or statusinformation begins with step S1910 where the configuration or statusinformation in the map structure is formatted to be sent. The structureof the map is such that either configuration or status information datamay be stored in the map. Once the data to be sent from the remotemonitoring workstation 911 to the central monitoring workstation 945 hasbeen formatted, the process proceeds to step S1911 where the data isencrypted. The Data Transfer 1107 module is configured to allow for alevel of encryption for a particular application to match thatapplication's needs without impacting the interface of the Data Transfer1107 module. Once the data is encrypted, the process proceeds to stepS1912 where the data is encoded. Once the data has been encrypted andencoded, the process proceeds to step S1913 where the data is sent viathe communication link described above, for example, as a MIMEattachment to an e-mail message. Once the data has been sent, theprocess ends.

[0112] The transfer of configuration or status information from theremote montoring workstation 911 to the central monitoring workstation945 has been described in the context of FIGS. 19A and 19B as using astore-and-forward protocol. Using a store-and-forward approach, forexample, SMTP and POP3, the e-mail message is sent via the SMTP server915 to a mail server, for example mail server POP3 943, in FIG. 9. Themail server POP3 will store the e-mail message until it is retrieved bythe intended recipient, which, in the example discussed above, is thecentral monitoring workstation 945. When the central monitoringworkstation 945 connects to the mail server POP3 943, the mail serverPOP3 will forward all messages it has stored that have the centralmonitoring workstation 945 as an intended recipient.

[0113]FIG. 19C is a class diagram illustrating one embodiment of theData Transfer 1107 module of FIG. 11 according to the present invention.The Data Transfer 1107 module is responsible for formatting theconfiguration or status information collected from the monitoreddevices, and for sending that information as an attachment to an e-mailmessage from a remote monitoring workstation 911 to a central monitoringworkstation 945, using, for example, SMTP. In one embodiment of thepresent invention, the monitoring information is sent as a MIMEattachment to an e-mail message. The Data Transfer 1107 module is alsoresponsible for encrypting the data and encoding the encrypted datausing, for example, Base64 encoding before sending the data. The DataTransfer 1107 module includes six classes: CDataTransfer 1405,CSendManager 1903, CAbsEncrypter 1905, CNullEncrypter 1907,CBase64Encoder 1909, and CSmtp 1911.

[0114] The CDataTransfer 1405 class provides the interface through whichthe functionality supported by the Data Transfer 1107 module isaccessed. In one embodiment of the present invention, the CDataTransfer1405 class includes four public methods through which all of thefunctionality of the Data Transfer 1107 module may be accessed. Thesemethods include a setDestination( ) method, a startSend( ) method, adataSend( ) method, and an endSend( ) method. The setDestination( )method is used to configure both a source and destination address for ane-mail from a remote monitoring workstation 911 to a central monitoringworkstation 945. The startSend( ) method is used to initiatecommunications between the remote monitoring workstation 911 and a SMTPserver 915. The dataSend( ) method is used to send the monitoringinformation as an e-mail message from the remote monitoring workstation911 to the central monitoring workstation 945 via the SMTP server 915.The dataSend( ) method supports the sending of either configurationinformation or status information. The endSend( ) method is used to shutdown the communication link after the configuration or statusinformation has been sent. While the Data Transfer 1107 module includessignificantly more capabilities, the complexities of these capabilitiesare hidden from the public interface.

[0115] Returning to FIG. 19C, the CSendManager 1903 class includesclasses that implement encrypting, encoding, and the management of acommunication link between the remote monitoring workstation 911 and theSMTP server 915. CAbsEncrypter 1905 is an abstract class providing theflexibility to add new encryption methods by adding new derived classesof CAbsEncrypter 1905, such as, for example, CNullEncrypter 1907. Thisclass structure provides the flexibility for an application to implementthe desired level of encryption, or to change an encryption methodwithout impacting the interface to the Data Transfer 1107 module.

[0116] The CBase64Encoder 1909 class provides base 64 encoding of theinformation before the information is sent. The CSmtp 1911 class isresponsible for managing the communication link between the remotemonitoring workstation 911 and the SMTP server 915. CSmtp 1911 makes useof the CSystemRegistry 1915 class for accessing the system registry todetermine a source and destination e-mail address for the e-mail messageheader to be sent to the SMTP server 915. Furthermore, CSmtp 1911 makesuse of the CSocket 1917 class available in the Microsoft foundationclasses (MFC) for establishing and taking down the communication linkbetween the remote monitoring workstation 911 and the SMTP server 915.

[0117]FIG. 20A is a collaboration diagram illustrating the interactionamong the classes of the Data Transfer 1107 module shown in FIG. 19Cwhen a remote monitoring workstation 911 initiates communication byestablishing a link to the SMTP server 915. In FIG. 20A, the user 2001corresponds to either the Device Monitor 1103 module or the DeviceInformation 1105 module. As shown in FIG. 20A, the process is initiatedby the user 2001 invoking the startSend( ) method of the CDataTransfer1405 class. In calling the startSend( ) method, the user 2001 indicateswhich type of information (e.g., configuration information or statusinformation) will be sent.

[0118]FIG. 20B illustrates an exemplary MIME attachment includingconfiguration information, as can be determined by the first line of theMIME attachment. FIG. 20C, on the other hand, illustrates an exemplaryMIME attachment including status information, as is also indicated bythe first line of the MIME attachment. As described above, it is thestartSend( ) method that ensures that the first line is appropriatelypopulated. The exemplary MIME attachments shown in FIGS. 20B and 20C areneither encrypted nor encoded.

[0119] Returning to FIG. 20A, once the user 2001 has requested theinitiation of communications, the CDataTransfer 1405 class will call thestartSend( ) method of the CSendManager 1903 class. The CSendManager1903 class manages the establishment of a communication link between theremote monitoring workstation 911 and the SMTP server 915 throughinteractions with the CSmtp 1913 class, which, in turn, interacts withthe CSocket 2013 class.

[0120] In order to use SMTP, the CSendManger 1903 class calls thecreateSocket( ) method of the CSmtp 1913 class to create a socket to theSMTP server 915 through which the SMTP commands will be sent. Next, theCSendManager 1903 class calls the connectSocket( ) method of the CSmtp1913 class to connect to that socket of the SMTP server 915. Inresponse, the CSmtp 1913 class will call the Connect( ) and Receive( )methods of the CSocket 2013 class to connect to the socket.

[0121] Once the socket has been established and connected to, theCSendManager 1903 class calls the sendHeloCommand( ) method of the CSmtp1913 class to send the HELO SMTP command to the SMTP server 915. Inresponse the CSmtp 1913 class will call the Send( ) method of theCSocket 2013 class to send the command to the socket of the SMTP server915, and subsequently call the Receive( ) method of the CSocket 2013class to receive a response from the socket of the SMTP server 915.Using the same approach, the CSendManager 1903 class will send the MAIL,RCPT, and DATA SMTP commands to the SMTP server 915 by respectivelycalling the sendMailCommand( ), sendRcptCommand( ), and sendDataCommand() methods of the CSmtp 1913 class. In response to each of the calls, theCSmtp 1913 class will call the Send( ) and Receive( ) methods of theCSocket 2013 class to send the commands to, and receive a response from,the socket of the SMTP server 915, respectively.

[0122] As would be understood by those of ordinary skill in the SMTPart, the HELO SMTP command is used by a client, for example, the remotemonitoring workstation 911, to identify itself to the SMTP server 915,the MAIL SMTP command is used to identify the originator of a mailmessage, the RCPT SMTP command is used to identify the recipient for amail message, and the DATA SMTP command is used to send the contents ofa mail message.

[0123] Next, the CSendManager 1903 class calls the sendMailHeader( )method of the CSmtp 1913 class to send the mail header for the e-mailmessage. The CSmtp 1913 class then calls the Send( ) method of theCSocket 2013 class to send the header to the socket of the SMTP server915. At this point, the information to be included in the e-mail messagecan be sent through the socket of the SMTP server 915. The datacorresponding to the appropriate information type of the monitoreddevices is sent by the CDataTransfer 1405 class calling the sendData( )method of the CSendManager 1903 class.

[0124]FIG. 21 is a collaboration diagram illustrating the interactionamong the classes of the Data Transfer 1107 module shown in FIG. 19C tosend either status or configuration data through e-mail in response tothe Device Monitor 1103 module or the Device Information 1105 module,respectively. In FIG. 21, the user 2001 corresponds to either the DeviceMonitor 1103 module or the Device Information 1105 module. As shown inFIG. 21, the process is initiated by the user 2001 calling the dataSend() method of the CDataTransfer 1405 class. The user 2001 sends the mapcontaining the configuration or status information as a parameter of thedataSend( ) method. The dataSend( ) method provides a single interface,through which both the Device Monitor 1103 module and the DeviceInformation 1105 module provide information to be sent to the DataTransfer 1107 module. In response, the CDataTransfer 1405 class callsthe sendData( ) method of the CSendManager 1903 class to send theinformation to the SMTP server 915. In one embodiment of the presentinvention, each call to the sendData( ) method of CSendManager 1903class sends one key/data value pair stored in the map to the socket(steps 8 and 9 shown in FIG. 21 are illustrative of this approach).Prior to sending the data, however, the CSendManager 1903 class callsthe encryptData( ) method of the CNullEncrypter 1907 class (or, asdescribed above, another class derived from the CAbsEncrypter 1905abstract class) to encrypt the data to be sent.

[0125] Next, the CSendManager 1903 class calls the encodeData( ) andgetEncodedString( ) methods of the CBase64Encoder 1911 class to encodethe encrypted data. To send the encrypted and encoded data, theCSendManager 1903 class calls the sendData( ) method of the CSmtp 1913class, which, in turn, calls the Send( ) method of the CSocket 2013class.

[0126]FIG. 22 is a collaboration diagram illustrating the interactionamong the classes of the Data Transfer 1107 module shown in FIG. 19Cwhen the sending of the configuration or status information throughe-mail has been completed. In FIG. 22, the user 2001 corresponds toeither the Device Monitor 1103 module or the Device Information 1105module. As shown in FIG. 22, the process is initiated by the user 2001calling the endSend( ) method of the CDataTransfer 1405 class. Inresponse, the CDataTransfer 1405 class calls the sendData( ) method ofthe CSendManager 1903 class to send data indicating the end of the datato be sent. While it is not shown in FIG. 22, the data sent will beencrypted and encoded following the same approach as that describedabove in the context of FIG. 21. Next, the CDataTransfer 1405 classcalls the endSend( ) method of the CSendManager 1903 class to completethe sending. The CSendManager 1903 class completes the sending of databy first calling the endOfData( ) and getEncodedString( ) methods of theCBase64Encoder 1911 class to obtain the last encoded information to besent. Next, the CSendManager 1903 class calls the sendData( ) method ofthe CSmtp 1913 class to send the last encoded encoded string containingdata. To send the last encoded string, the CSmtp 1913 class calls theSend( ) method of the CSocket 2013 class.

[0127] Next, the CSendManager 1903 class calls the sendEndOfMail( )method of the CSmtp 1913 class to send the end of the mail data. Inturn, the CSmtp 1913 class calls the Send( ) method of the CSocket 2013class to send the end of the mail data through the socket of the SMTPserver 915 followed by a call to the Receive( ) method of the CSocket2013 class to obtain a response from the socket. Next, the CSendManager1903 class calls the sendQuitCommand( ) method of the CSmtp 1913 classto send the QUIT SMTP command to the socket of the SMTP server 915 toterminate the e-mail session between the remote monitoring workstation911 and the SMTP server 915. In response, the CSmtp 1913 class calls theSend( ) and Receive( ) methods of the CSocket 2013 class to send theQUIT command and obtain a response from the socket.

[0128]FIG. 23 is a collaboration diagram illustrating the interactionamong the classes of the Data Transfer 1107 module shown in FIG. 19C toset up the system registry of the remote monitoring workstation 911 forsending device configuration and status information through e-mail tothe central monitoring workstation 945. As shown in FIG. 23, the processis initiated by a call to the setDestination( ) method of theCDataTransfer 1405 class by the Interface 1101. In response, theCDataTransfer 1405 class calls the setDestination( ) method of theCSendManager 1403 class, which, in turn, calls the setDestination( )method of the CSmtp 1913 class. To store the information in the systemregistry, the CSmtp 1913 class calls the setSMTPServer( ), setFromAddr(), and setRcptAdd( ) methods of the CSystemRegistry 1915 class to storethe SMTP Server, the from address, and the recipient address to be usedin sending configuration or status information to the central monitoringworkstation 945, respectively, in the system registry of the remotemonitoring workstation 911.

[0129]FIG. 24 is a class diagram illustrating one embodiment of the ODBCInterface 1109 module of FIG. 11 according to the present invention. TheODBC Interface 1109 module is responsible for interfacing with thedatabase 913 that maintains the information pertaining to the SNMPdevices being monitored by a particular remote monitoring workstation911. In this embodiment, the database is registered as an ODBC database,and, therefore, the database 913 has available the appropriatesupporting ODBC drivers. The ODBC Interface 1109 module includes fiveclasses: CSendODBCInterface 2401, CDeviceInformationData 2403,CDeviceDatabase 2407, CDevicePersistentStatus 2411, andCDevicePerDatabase 2413. The CSendODBCInterface 2401 class provides theinterface through which the functionality supported by the ODBCInterface 1109 module is accessed.

[0130] The CDeviceInformationData 2403 class provides methods forobtaining and storing configuration information of the monitored devicesin the database 913. The CDeviceDatabase 2407 class provides aninterface between the CDeviceInformationData 2403 class and the actualdatabase 913 that contains the configuration information. TheCDeviceInformationData 2403 class uses the DeviceInfo structure to storethe configuration information in the database 913.

[0131] The CDevicePersistentStatus 2411 class provides methods forobtaining and storing the first type of information of the monitoreddevices in the database. The CDevicePerDatabase 2407 provides aninterface between the CDevicePersistentStatus 2411 class and the actualdatabase that contains the first type of information. TheCDevicePersistentStatus 2411 class uses the DevicePerStatus structure tostore the first type of information in the database 913.

[0132] Both the CDeviceDatabase 2407 class and the CDevicePerDatabase2413 class are derived from the CRecordset 2417 class available in theMicrosoft Foundation Classes (MFC).

[0133] Obviously, numerous modifications and variations of the presentinvention are possible in light of the above teachings. It is thereforeto be understood that within the scope of the appended claims, theinvention may be practiced otherwise than as specifically describedherein.

What we claim is:
 1. A method for sending configuration informationcorresponding to a network device from a remote monitor to a centralmonitor, comprising the steps of: querying a digital repository by theremote monitor for the configuration information, the configurationinformation including a local unique identifier corresponding to thenetwork device; obtaining a globally unique identifier from the networkdevice by the remote monitor using the local unique identifier to accessthe network device using a network management protocol; and sending theconfiguration information and the globally unique identifier by theremote monitor to the central monitor as a message using a transferprotocol.
 2. The method of claim 1, wherein the local unique identifiercomprises an Internet protocol address of the network device.
 3. Themethod of claim 1, wherein the globally unique identifier comprises aphysical address of the network device.
 4. The method of claim 1,wherein the physical address comprises a media access control address ofthe network device.
 5. The method of claim 1, wherein the networkmanagement protocol comprises a simple network management protocol. 6.The method of claim 1, wherein the transfer protocol comprises astore-and-forward protocol.
 7. The method of claim 1, wherein thetransfer protocol comprises a simple mail transfer protocol.
 8. Themethod of claim 1, wherein the transfer protocol comprises a directconnection protocol.
 9. The method of claim 1, wherein the transferprotocol comprises at least one of a file transfer protocol and a hypertext transfer protocol.
 10. The method of claim 1, wherein the messagecomprises an Internet e-mail message.
 11. The method of claim 1,wherein: the message comprises an Internet e-mail message, and theconfiguration information is sent as an attachment to the message. 12.The method of claim 1, wherein: the message comprises an Internet e-mailmessage, and the configuration information is sent as a multipurposeInternet mail extensions attachment to the message.
 13. The method ofclaim 1, further comprising the step of: encrypting the configurationinformation by the remote monitor prior to the sending step.
 14. Themethod of claim 13, further comprising the step of: encoding theconfiguration information by the remote monitor after the encryptingstep and prior to the sending step.
 15. The method of claim 14, whereinthe encoding step comprises encoding the configuration information usinga base 64 encoding.
 16. The method of claim 1, further comprising thestep of: encoding the configuration information by the remote monitorprior to the sending step.
 17. The method of claim 16, wherein theencoding step comprises encoding the configuration information using abase 64 encoding.
 18. A computer-implemented system for sendingconfiguration information corresponding to a network device from aremote monitor to a central monitor, comprising: a processor; and acomputer readable medium encoded with processor readable instructionsthat when executed by the processor implement a database managementmechanism configured to query a database for the configurationinformation, the configuration information including a local uniqueidentifier corresponding to the network device, a device managementmechanism configured to obtain a globally unique identifier from thenetwork device using the local unique identifier to access the networkdevice using a network management protocol, and a sending mechanismconfigured to send the configuration information and the globally uniqueidentifier from the remote monitor to the central monitor as a messageusing a transfer protocol.
 19. The system of claim 18, wherein the localunique identifier comprises an Internet protocol address of the networkdevice.
 20. The system of claim 18, wherein the globally uniqueidentifier comprises a physical address of the network device.
 21. Thesystem of claim 18, wherein the globally unique identifier comprises amedia access control address of the network device.
 22. The system ofclaim 18, wherein the network management protocol comprises a simplenetwork management protocol.
 23. The system of claim 18, wherein thetransfer protocol comprises a store-and-forward protocol.
 24. The systemof claim 18, wherein the transfer protocol comprises a simple mailtransfer protocol.
 25. The system of claim 18, wherein the transferprotocol comprises a direct connection protocol.
 26. The system of claim18, wherein the transfer protocol comprises at least one of a filetransfer protocol and a hyper text transfer protocol.
 27. The system ofclaim 18, wherein the message comprises an Internet e-mail message. 28.The system of claim 18, wherein: the message comprises an Internete-mail message, and the configuration information is sent as anattachment to the message.
 29. The system of claim 18, wherein: themessage comprises an Internet e-mail message, and the configurationinformation is sent as a multipurpose Internet mail extensionsattachment to the message.
 30. The system of claim 18, wherein thecomputer readable medium is further encoded with processor readableinstructions that when executed by the processor further implements anencryption mechanism configured to encrypt the configuration informationprior to sending the configuration information.
 31. The system of claim30, wherein the computer readable medium is further encoded withprocessor readable instructions that when executed by the processorfurther implements an encoding mechanism configured to encode theconfiguration information after the encryption mechanism encrypts theconfiguration information and prior to sending the configurationinformation.
 32. The system of claim 31, wherein the encoding mechanismis further configured to encode the configuration information using abase 64 encoding.
 33. The system of claim 18, wherein the computerreadable medium is further encoded with processor readable instructionsthat when executed by the processor further implements an encodingmechanism configured to encode the configuration information prior tosending the configuration information.
 34. The system of claim 33,wherein the encoding mechanism is further configured to encode theconfiguration information using a base 64 encoding.
 35. A computerprogram product, comprising: a computer storage medium; and a computerprogram code mechanism embedded in the computer storage medium forcausing a computer to send configuration information corresponding to anetwork device from a remote monitor to a central monitor, the computerprogram code mechanism having a first computer code device configured toquery a database for the configuration information, the configurationinformation including a local unique identifier corresponding to thenetwork device, a second computer code device configured to obtain aglobally unique identifier from the network device using the localunique identifier to access the network device using a networkmanagement protocol, and a third computer code device configured to sendthe configuration information and the globally unique identifier fromthe remote monitor to the central monitor as a message using a transferprotocol.
 36. The computer program product of claim 35, wherein thelocal unique identifier comprises an Internet protocol address of thenetwork device.
 37. The computer program product of claim 35, whereinthe globally unique identifier comprises a physical address of thenetwork device.
 38. The computer program product of claim 35, whereinthe globally unique identifier comprises a media access control addressof the network device.
 39. The computer program product of claim 35,wherein the network management protocol comprises a simple networkmanagement protocol.
 40. The computer program product of claim 35,wherein the transfer protocol comprises a store-and-forward protocol.41. The computer program product of claim 35, wherein the transferprotocol comprises a simple mail transfer protocol.
 42. The computerprogram product of claim 35, wherein the transfer protocol comprises adirect connection protocol.
 43. The computer program product of claim35, wherein the transfer protocol comprises at least one of a filetransfer protocol and a hyper text transfer protocol.
 44. The computerprogram product of claim 35, wherein the message comprises an Internete-mail message.
 45. The computer program product of claim 35, wherein:the message comprises an Internet e-mail message, and the configurationinformation is sent as an attachment to the message.
 46. The computerprogram product of claim 35, wherein: the message comprises an Internete-mail message, and the configuration information is sent as amultipurpose Internet mail extensions attachment to the message.
 47. Thecomputer program product of claim 35, wherein the computer program codemechanism further having a fourth computer code device configured toencrypt the configuration information prior to sending the configurationinformation.
 48. The computer program product of claim 47, wherein thecomputer program code mechanism further having a fifth computer codedevice configured to encode the configuration information after thefourth computer code device encrypts the configuration information andprior to sending the configuration information.
 49. The computer programproduct of claim 48, wherein the fifth computer code device is furtherconfigured to encode the configuration information using a base 64encoding.
 50. The computer program product of claim 35, wherein thecomputer program code mechanism further having a fourth computer codedevice configured to encode the configuration information prior tosending the configuration information.
 51. The computer program productof claim 50, wherein the fourth computer code device is furtherconfigured to encode the configuration information using a base 64encoding.